Grokking SQL for Tech Interviews
Rate this course
Ask Author
Contribute
Back to course home

1% completed

Vote For New Content
Introduction
Course Overview
What is RDBMS?
What is SQL?
A Quick Review of SQL
Read data from table
WHERE Clause
Operators
Handle NULLs in SQL
DISTINCT Clause
ORDER BY Clause
LIMIT and OFFSET
GROUP BY
HAVING
Aggregate Functions
Order of Execution
Order of SQL Query Execution
SQL Functions
Number Functions
String Functions
Date Functions
Nested Queries
Nested Query
Types of Subqueries
JOINS
Introduction
INNER JOIN
LEFT OUTER JOIN
RIGHT OUTER JOIN
FULL OUTER JOIN
SELF JOIN
SET Operations
What are SET operations?
UNION
INTERSECT
EXCEPT
A Quick Review of DDL
Keys in SQL
CREATE
ALTER
DROP
TRUNCATE
Indexes
A Quick Review of DML
INSERT
UPDATE
DELETE
Database Backup & Restore
Backup Database
Restore Database
Interview Problems - Easy
1. Major Cities
2. Not boring movies
3. Triangle Judgement
4. Biggest Single Number
5. Product Sales Analysis I
6. Product Sales Analysis II
7. Game Play Analysis I
8. Game Play Analysis II
9. Queries Quality and Percentage
10. Average Selling Price
11. Weather Type in Each Country
12. Students and Examinations
13. Ads Performance
14. Group Sold Products By The Date
15. Employee Email Verification
16. Sellers With No Sales
17. Average Time of Process
18. Find Followers Count
19. Ad-Free Sessions
20. Bikes Last Time Used
21. Daily User Engagement Levels
22. Employee Attendance Record
23. Library Book Loans
24. Customer Purchase Summary
25. Long Comments (Easy)
26. Unused Accounts
27. Patient Appointment No-Shows
28. Books and Authors
29. High School Attendance
30. Employee Absences
31. Green Product Identification (Easy)
32. Employee Department Exclusion (Easy)
33. Sales Person (Easy)
34. Employee Task Tracking (Easy)
Interview Problems - Medium
1. Winning Candidate
2. Second Degree Follower
3. 2nd Highest Salary
4. Game Play Analysis III
5. Game Play Analysis IV
6. Active Businesses
7. Product Price on a Specific Date
8. Monthly Transactions II
9. Team Scores in Football Tournament
10. Page Recommendations
11. Running Total for Different Genders
12. Evaluate Boolean Expression
13. Active Users
14. Find Interview Candidates
15. Suspicious Bank Accounts
16. Order Fulfillment Rate (Medium)
17. Last Person to Fit in the Elevator (Medium)
18. Retail Expansion Analysis (Medium)
19. Employee Collaboration Networks (Medium)
20. Second Fastest Time in Races (Medium)
Interview Problems - Hard
1. Trips and Users
2. Human Traffic of Stadium
3. Students Report By Geography
4. Game Play Analysis V
5. Number of Transactions per Visit
6. Find the Quiet Students in All Exams
7. First and Last Call On the Same Day
8. Build the Equation
9. Longest Winning Streak
10. Dynamic Pivoting of a Table
11. Dynamic Unpivoting of a Table
12. Generate the Invoice
13. Popularity Percentage
14. Viewers Turned Streamers
15. Status of Flight Tickets
1. High Performing Employees (Easy)
2. Student Course Averages (Easy)
3. Library Book Checkout Percentage (Easy)
4. Employee Performance and Improvement Rate (Easy)
5. Find Popular Posts (Easy)
6. Main Office Assignment for Each Employee (Easy)
7. Rectangle Validation (Easy)
8. Library Book Checkouts by Date (Easy)
9. Same-Day Appointment Fulfillment (Medium)
10. Departments with High Earning Employees (Medium)
11. Students Who Attended All Courses (Medium)
12. Library Book Checkouts First Year (Medium)
13. Repeated Values in Sequence (Medium)
14. School Top Achievers by Subject (Hard)
15. Status of Flight Tickets

Problem

Table: Flights

+-------------+------+
| Column Name | Type |
+-------------+------+
| flight_id   | int  |
| capacity    | int  |
+-------------+------+
flight_id column contains distinct values.
Each row of this table contains flight id and capacity.

Table: Passengers

+--------------+----------+
| Column Name  | Type     |
+--------------+----------+
| passenger_id | int      |
| flight_id    | int      |
| booking_time | datetime |
+--------------+----------+
passenger_id column contains distinct values.
booking_time column contains distinct values.
Each row of this table contains passenger id, booking time, and their flight id.

Problem Definition

Passengers book tickets for flights in advance. If a passenger books a ticket for a flight and there are still empty seats available on the flight, the passenger's ticket will be confirmed. However, the passenger will be on a waitlist if the flight is already at full capacity.

Write a solution to determine the current status of flight tickets for each passenger.

Return the result table ordered by passenger_id in ascending order.

Example

Image

Output

Image

Try It Yourself

MYSQL

. . . .

Flights =

Passengers =

Solution

To determine the current status of flight tickets for each passenger—whether their booking is Confirmed or on the Waitlist—we analyze the Flights and Passengers tables. We ca efficiently accomplishes this by utilizing window functions and conditional logic to rank passengers based on their booking times relative to flight capacities. Below is a comprehensive breakdown of the approach, step-by-step execution, and detailed explanations for each line of the SQL query.

Approach Overview

  1. Combine Flight and Passenger Data:

    • Merge data from Flights and Passengers tables to associate passengers with flight capacities.
  2. Rank Passengers per Flight by Booking Time:

    • Assign a rank to each passenger within their respective flights based on their booking times.
  3. Determine Ticket Status:

    • Compare each passenger's rank with the flight's capacity to assign 'Confirmed' or 'Waitlist' status.
  4. Present the Final Results:

    • Display each passenger's ID alongside their ticket status, ordered by passenger_id in ascending order.

SQL Query

SELECT passenger_id, IF(Rank() over( PARTITION BY flight_id ORDER BY booking_time) <= capacity, 'Confirmed', 'Waitlist') AS Status FROM Passengers LEFT JOIN Flights USING(flight_id) ORDER BY passenger_id;

Step-by-Step Approach

Step 1: Combine Flight and Passenger Data

Merge the Passengers table with the Flights table to associate each passenger with the capacity of their booked flight. This association is crucial for determining whether a passenger's booking is confirmed or placed on a waitlist based on the flight's capacity.

SQL Snippet:

FROM Passengers LEFT JOIN Flights USING(flight_id)

Explanation:

  1. Passengers LEFT JOIN Flights USING(flight_id)
    • Performs a left join between the Passengers table and the Flights table based on the common column flight_id.
    • LEFT JOIN ensures that all records from Passengers are retained, even if there is no matching flight_id in Flights. However, since every flight_id in Passengers should correspond to a valid flight_id in Flights, this ensures comprehensive data association.
    • USING(flight_id) simplifies the join condition by specifying the common column directly, eliminating the need to prefix columns with table aliases.

Intermediate Output After Step 1:

+--------------+-----------+---------------------+-----------+ | passenger_id | flight_id | booking_time | capacity | +--------------+-----------+---------------------+-----------+ | 101 | 1 | 2023-07-10 16:30:00 | 2 | | 102 | 1 | 2023-07-10 17:45:00 | 2 | | 103 | 1 | 2023-07-10 12:00:00 | 2 | | 104 | 2 | 2023-07-05 13:23:00 | 2 | | 105 | 2 | 2023-07-06 09:00:00 | 2 | | 106 | 3 | 2023-07-08 11:10:00 | 1 | | 107 | 3 | 2023-07-08 09:10:00 | 1 | +--------------+-----------+---------------------+-----------+

Step 2: Rank Passengers per Flight by Booking Time and Assign Ticket Status

Assign a rank to each passenger within their respective flights based on their booking_time. Passengers who book earlier receive a higher priority (lower rank number), while those who book later are ranked lower. This ranking is essential to determine which passengers secure a confirmed seat based on flight capacity.

SQL Snippet:

IF(Rank() over( PARTITION BY flight_id ORDER BY booking_time) <= capacity, 'Confirmed', 'Waitlist') AS Status

Explanation:

  1. Rank() OVER (PARTITION BY flight_id ORDER BY booking_time)
    • Rank(): A window function that assigns a rank to each row within a partition.
    • OVER: Defines the window for the rank calculation.
    • PARTITION BY flight_id: Divides the dataset into partitions where each partition contains rows with the same flight_id. This ensures that ranking is performed separately for each flight.
    • ORDER BY booking_time: Orders the rows within each partition by booking_time in ascending order. Passengers who booked earlier receive a higher priority (lower rank number).
  2. IF(Rank() OVER (...) <= capacity, 'Confirmed', 'Waitlist') AS Status
    • IF(condition, value_if_true, value_if_false): A conditional function that returns value_if_true if the condition is true, else returns value_if_false.
    • Rank() OVER (...) <= capacity: Checks if the passenger's rank is within the flight's capacity.
      • If true: The passenger's booking is within the available capacity, hence 'Confirmed'.
      • If false: The flight is already at full capacity, and the passenger is placed on the 'Waitlist'.
    • AS Status: Aliases the resulting value as Status.

Intermediate Output After Step 2 (with Status):

+--------------+-----------+---------------------+-----------+-----------+ | passenger_id | flight_id | booking_time | capacity | Status | +--------------+-----------+---------------------+-----------+-----------+ | 101 | 1 | 2023-07-10 16:30:00 | 2 | Confirmed | | 102 | 1 | 2023-07-10 17:45:00 | 2 | Waitlist | | 103 | 1 | 2023-07-10 12:00:00 | 2 | Confirmed | | 104 | 2 | 2023-07-05 13:23:00 | 2 | Confirmed | | 105 | 2 | 2023-07-06 09:00:00 | 2 | Confirmed | | 106 | 3 | 2023-07-08 11:10:00 | 1 | Waitlist | | 107 | 3 | 2023-07-08 09:10:00 | 1 | Confirmed | +--------------+-----------+---------------------+-----------+-----------+

Step 3: Present the Final Results

Display each passenger's ID alongside their ticket status, ordered by passenger_id in ascending order as specified.

SQL Snippet:

SELECT passenger_id, IF(Rank() over( PARTITION BY flight_id ORDER BY booking_time) <= capacity, 'Confirmed', 'Waitlist') AS Status FROM Passengers LEFT JOIN Flights USING(flight_id) ORDER BY passenger_id;

Explanation:

  1. ORDER BY passenger_id;
    • Orders the final result set by passenger_id in ascending order to meet the problem's requirement.

Final Output:

+--------------+-----------+ | passenger_id | Status | +--------------+-----------+ | 101 | Confirmed | | 102 | Waitlist | | 103 | Confirmed | | 104 | Confirmed | | 105 | Confirmed | | 106 | Waitlist | | 107 | Confirmed | +--------------+-----------+
14. Viewers Turned Streamers
1. High Performing Employees (Easy)
Mark as Completed

On this page

Problem

Problem Definition

Example

Output

Try It Yourself

Solution

Approach Overview

SQL Query

Step-by-Step Approach